|
|
|
In this section, we describe best practices for LDAP optimizations.
Each LDAP implementation is unique, so it is not possible to give an exact set of steps for changes on the directory server. However, there are a few best practices that apply globally to all LDAP implementations, as follows:
- Avoid using custom attributes that are not indexed. Certain LDAP implementations require a full text index search of the directory, which increases the time it takes to process a search request. The search time for non-default attributes can be double or more that the time it takes to search on the default attributes. You should use existing attributes whenever possible.
- Index the directory and all commonly accessed attributes.
- Assign an objectclass specifically for Sametime users. By assigning a specific objectclass, it is possible to restrict other LDAP entries such as dummy ids, shared ids, and so on, which may not be used as part of the Sametime environment.
- Do not set the LDAP server to disconnect idle connections within five minutes of establishing them. The Sametime server keeps a persistent connection to the LDAP server to reduce the cost of establishing a new connection every time a new request has to be sent. Prematurely disconnecting the LDAP connection will only delay the time it takes to process name lookup requests.
- Load Balance the LDAP environment. By load balancing the environment, the Sametime server can send over more requests at a time because the load balancer distributes connections to different LDAP servers according to the policy. It also prevents disruption of service in the case of an LDAP server failure.
For complete LDAP optimization recommendations, see Best Practices for using LDAP with Lotus Sametime. The article contains a troubleshooting table to help you isolate and solve LDAP problems.
|